-
Notifications
You must be signed in to change notification settings - Fork 16.8k
incubator/kube-downscaler - Expand configuration options for service account #23058
Conversation
Hi @patrungel. Thanks for your PR. I'm waiting for a helm member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign @Pluies |
Hi @patrungel! This is a breaking change by removing Looking at other popular charts (like cluster-autoscaler, coredns or prometheus-operator), it looks like the usual approach to do that would be with:
But I haven't seen any other chart that define either labels or pull secrets for automatically-created serviceaccounts. I'd argue that if someone needs that level of customisation, they should probably create the serviceAccount separately and define it with What do you think? cc @Rowern |
Thanks for the review, @Pluies .
I'll comply with the above.
UPD: all items but the version are now committed. |
e58e014
to
becfc21
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree on the breaking character of the change. Is it okay ot up major version, considering the chart is in pre-release (major version 0)? https://semver.org/#how-do-i-know-when-to-release-100
I guess that makes sense, especially because we're in the incubator
part of the charts :)
The imagePullSecrets part looks fine. 👍
Just a couple of notes on this PR and this is mergeable!
incubator/kube-downscaler/README.md
Outdated
| `resources` | Downscaler pod resource requests & limits | `{}` | | ||
| `securityContext` | SecurityContext to apply to the downscaler pod | `{}` | | ||
| `rbac.create` | If true, create & use RBAC resources | `true` | | ||
| `serviceAccount.create` | If true, create & use a ServiceAccount | `""` | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The default here should be true
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed that one, thanks!
apiVersion: v1 | ||
kind: ServiceAccount | ||
metadata: | ||
name: {{ include "kube-downscaler.fullname" . }} | ||
name: {{ include "kube-downscaler.serviceAccountName" . }} | ||
namespace: {{ .Release.Namespace }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this line needed? 🤔 I would think it creates resources in the release namespace by default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's an ongoing discussion for about a year or so: helm/helm#5465
While in general helm is supposed to place items into the correct namespace, there are use-cases depending on namespace field to be present. I err on the side of caution here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤷 fine; probably should be added to other resources for consistency, but I won't hold the PR based on this!
Just for the sake of clarity, is it going to be |
becfc21
to
c80cae9
Compare
@patrungel let's keep 0.5.0 👍 /ok-to-test /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: patrungel, Pluies The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
Edit: deleted comment |
Edit: deleted comment |
@scottrigby uh, this PR is for the kube-downscaler, as far as I know it has nothing to do with Prometheus – did you actually mean to close it or was it a mistake? |
@Pluies you're right 👌 This was my mistake somehow from the previous comment, then last night my search picked it up again. Thanks 🙂 |
The present introduces support for imagePullSecrets and ServiceAccount annotations Signed-off-by: Danil Mironov <[email protected]>
c80cae9
to
08f6f24
Compare
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
This issue is being automatically closed due to inactivity. |
Is this a new chart
No
What this PR does / why we need it:
The present introduces support for imagePullSecrets, annotations, and extra labels for ServiceAccount in use
I moved SA options out of RBAC tree to decouple SA configuration from the one for roles.
I took the liberty of incrementing minor version of the chart as the change is a feature increment.
Special notes for your reviewer:
None
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]
[stable/mychartname]
)